-
Notifications
You must be signed in to change notification settings - Fork 759
Add description field in task and trigger protos #6722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v2
Are you sure you want to change the base?
Conversation
Signed-off-by: Alex Wu <[email protected]>
|
Bito Automatic Review Skipped - Branch Excluded |
wild-endeavor
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add validation everywhere?
flyteidl2/task/environment.proto
Outdated
| ]; | ||
|
|
||
| // Optional description of environment | ||
| string description = 2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add the validation here also, we can always remove it in the future but i think safer to add for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added string length validation to every description field, thanks!
|
|
||
| // Link to source code used to define this entity | ||
| message SourceCode { | ||
| string link = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can also consider sending a remote, a file path, and a line number, and letting the backend construct the actual link. but this is okay for now.
flyteidl2/task/task_definition.proto
Outdated
| string link = 1; | ||
| } | ||
|
|
||
| message DescriptionEntity { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really don't like this name but I can't think of anything better. cc @pingsutw any ideas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Documentation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wild-endeavor Is the proto name "DocumentationEntity" sounds good to you?
Signed-off-by: Alex Wu <[email protected]>
Signed-off-by: Alex Wu <[email protected]>
|
Bito Automatic Review Skipped - Branch Excluded |
Signed-off-by: Alex Wu <[email protected]>
Signed-off-by: Alex Wu <[email protected]>
Signed-off-by: Alex Wu <[email protected]>
|
Bito Automatic Review Skipped - Branch Excluded |
Signed-off-by: Alex Wu <[email protected]>
Signed-off-by: Alex Wu <[email protected]>
Signed-off-by: Alex Wu <[email protected]>
|
Bito Automatic Review Skipped - Branch Excluded |
Signed-off-by: Alex Wu <[email protected]>
Signed-off-by: Alex Wu <[email protected]>
|
Bito Automatic Review Skipped - Branch Excluded |
Why are the changes needed?
Add description field to Task and Trigger protos
What changes were proposed in this pull request?
Update proto and regenerate
Check all the applicable boxes